home *** CD-ROM | disk | FTP | other *** search
- Path: sdd.hp.com!inn
- From: Jeff Grimmett <jgrimm@sdd.hp.com>
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: YASL (was: AsynchIO (was: fastest file read method ??))
- Date: 28 Jan 1996 20:05:37 GMT
- Organization: Hewlett-Packard Company
- Message-ID: <4egkuh$j1q@news.sdd.hp.com>
- References: <w9YbsMD4ACazz9@jeff.dame.shnet.org> <w+RYXMD4FC8aRz1@_crisi.blackbox.shnet.org> <4dsalp$t68@news1.halcyon.com> <4du0ju$84b@news.sdd.hp.com> <4e2e76$9k3@toad.stack.urc.tue.nl> <4e3j8v$jd0@news.sdd.hp.com> <4e7si4$ore@tuegate.tue.nl> <4e8asc$rht@news.sdd.hp.com> <1349.6599T1259T2701@amiga.pp.se>
- NNTP-Posting-Host: hpsdv330.sdd.hp.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.2N (Windows; I; 16bit)
-
- mikael.berglund@amiga.pp.se (Mikael Berglund) wrote:
-
- >>My opinion as such differs from yours. I have over a dozen so-called
- >>shared libraries in my LIBS: directory that are shared by ONE program,
- >>this is SHARING? What uses hyperion.library and centurion.library? One
- >>program that I'm aware of. If something else does, I don't have it.
- >
- >But you miss one thing here. The ONE program using the library would still
- >have to link it into the code thus making the code bigger and take up more
- >or less the same diskspace.
-
- Fine. But at least if it's linked, it's in the same place. If/when I
- decide that this program is a waste of electrons, simply deleting that
- one program and/or its directory will take care of things, nice and tidy,
- whereas if it sneaks a shared lib in on me, it'll still be there in the
- year 2000, and I'll still be wondering how it got there.
-
- >Granted, programmers should not place the library by default in LIBS: but
- >use the home directory if they are fairly sure no one else is using it.
- Kinda negates having it in a shared library, then, doesn't it?
-
- >From a programmers point of view there are many reasons to place code in a
- >shared library the most significant would be code reusability.
-
- I will not deny this at all.
-
- > Also it is
- >easy to flush libraries from memory that you do not need opposed to the
- >overlay technique which IMHO leaves many wishes to be satisfied.
-
- Irrelevant to my point, really. Whether the code is in an overlay, in
- the program itself, or in BeepBop-a-ReeBop.library is irrelevant. If no
- one else will be using the library, it serves no purpose than to confuse
- things.
-
- I'd just like to see a little judgement used by developers, is all. If
- there's no real compelling reason to put it in a library, it shouldn't
- be. But, if you do, DOCUMENT IT and make the required files available to
- other developers so that it is NOT a waste.
-
-